Resolve Data Errors
Errors received on a data sync can occur for several reasons. Administrators can use the common error guide below to resolve errors and re-sync the data.
Errors on the Sync Results page can be easily identified by the Error icon, a red triangle with an exclamation point. Data results can be filtered to show only errors, if desired.
Common User Data Errors
The error messages listed below are commonly received user record errors caused by data issues found in the source data being shared with Benchmark.
After resolving the data issue that caused the error you can Force Sync the user record or if multiple data errors were resolved you can Run a Data Sync to bring in all the updates at once.
Message: Grade level is required for students.
This error is specific to student records. Providing a grade level is a requirement for student records to be created. If this error is received there is no grade level available in this user’s source data.
Recommended Action: Add a valid grade level to the student’s source data.
Message: “grade” is not a supported grade level.
This error is specific to student records. The grade value provided in the source data (and listed in the error) for the student is not supported.
Recommended Action: Update the grade level in the student’s source data to a supported grade level. Supported grade levels can vary slightly between third party data sources.
Message: User is associated to “X” unlicensed schools [“school id”, “school id”, “school id”]
Benchmark only syncs data for users and classes associated to schools that are licensed for content. This error is received if a user is associated to an unlicensed school shared in the data. Receiving this error does not mean that a user record wasn’t created or updated.
Recommended Action: Adjust the sharing rules in the source data to only share licensed schools with Benchmark. For instance, in most cases it is not necessary to share high schools and associated data.
Message: Data Constraint: “email address” must be unique and already exists for a user in the district.
Email addresses must be unique for teachers and administrators in a district. This error is received for a user record on sync if the associated email address already exists for a user account.
Recommended Action: Search the email address in Tech Admin in the teacher, administrator, or deactivated sections. The email address can then be removed or altered to allow the new account to come in on sync.
Message: Data Constraint: SIS ID “sis id” must be unique and already exists for a user in the district.
SIS IDs must be unique across all users in a district. This error is received for a user record on sync if the associated SIS ID already exists for a user account.
Recommended Action: Search the SIS ID in Tech Admin in the student, teacher, administrator, or deactivated sections. The SIS ID can then be removed or altered to allow the new account to come in on sync.
Message: Data Constraint: External ID “external id” must be unique and already exists for a user in the district.
External IDs (Clever ID, SourcedID, etc.) must be unique across all users in a district. This error is received for a user record on sync if the associated External ID already exists for a user account.
Recommended Action: Search the External ID in Tech Admin in the student, teacher, administrator, or deactivated sections. The External ID can then be removed or altered to allow the new account to come in on sync.
Message: Data Constraint: SSO ID "sso id” must be unique and already exists for a user in the district.
SSO IDs (Clever ID, SourcedID, etc.) must be unique across all users in a district. This error is received for a user record on sync if the associated SSO ID already exists for a user account.
Recommended Action: Search the SSO ID in Tech Admin in the student, teacher, administrator, or deactivated sections. The SSO ID can then be removed or altered to allow the new account to come in on sync.
Message: “role name” is not a supported role.
Some data sources can include user roles that are not supported in Benchmark Universe or cannot be mapped to a valid Benchmark Universe role. Examples of unsupported roles are ‘Proctor’, ‘Parent’, ‘Guardian’, etc.
Recommended Action: Reassign the user’s role to a Benchmark Universe supported role such as Student, Teacher, or Administrator. Another option is to completely filter out the invalid role from your shared dataset.
Common Class Data Errors
The error messages listed below are commonly received class record errors caused by data issues found in the source data being shared with Benchmark.
After resolving the data issue that caused the error you can Force Sync the class record or if multiple data errors were resolved you can Run a Data Sync to bring in all the updates at once.
Message: Class is associated to an unlicensed school: "school id”.
Benchmark only syncs data for users and classes associated to schools that are licensed for content. This error is received if a class is associated to an unlicensed school shared in the data.
Recommended Action: Adjust the sharing rules in the source data to only share licensed schools with Benchmark. For instance, in most cases it is not necessary to share high schools and associated data.
Message: Class SIS ID "sis id” already exists for this district term.
SIS ID is a required field for a class and must be unique within a given district term. This error is received for a class record on sync if the associated SIS ID already exists for a class.
Recommended Action: Search the SIS ID in Tech Admin in the classes section. The SIS ID can then be altered to allow the new account to come in on sync.
Message: Class with associated assignments cannot be deleted on sync.
Benchmark does not allow classes that have associated assignments in Benchmark Universe to be deleted on an automated sync. Deleting classes that have assignments, and potentially assessments with associated scores, can affect data in the Reporting suite.
Recommended Action: Classes that have associated assignments can be deleted manually by an administrator in Tech Admin.
Message: User(s) could not be added to class. Identifiers of missed users: “external id”, “external id”.
This error is received when synching a class record if the class roster in the source data has students or teachers that are not yet found in our system.
Recommended Action: Use the listed external id(s) to search for the user in the shared source data and ensure the user is being shared with Benchmark. Also, check user-level sync errors to determine if a data error is stopping the user record from being created.